Category
5 articles
Decommissioning an ageing ESB or middleware layer is an architecture discipline in its own right. This article sets out a practical retirement sequence for UK organisations: discover live traffic, freeze new dependencies, run parallel periods with exit criteria, prove the negative and leave an audit trail that survives the server.
Energy is becoming a board-level concern, but integration estates are rarely metered at the interface level. A lightweight carbon ledger can make batch windows, retry storms and always-on connectors visible to finance and sustainability teams without pretending to be a full life-cycle assessment.
Integration incidents cluster around dates that are entirely predictable. A calendar-aware operating model — with freeze tiers, regional holiday logic and rehearsed year-end runbooks — is a more useful control than a generic change policy.
Batch, change data capture and event streams each carry a different operational bill. This practical guide gives UK teams a decision framework based on latency, volume, failure tolerance and in-house capability, with the 2am debug test as the final gate.
UK buyers now have more contractual leverage over cloud switching than at any point in the last decade. The remaining obstacle is architectural: identities, event schemas and data pipelines that only make sense inside one provider. Portability has to be designed into the integration layer, not negotiated into the contract.